home *** CD-ROM | disk | FTP | other *** search
- Path: news.cybertron.com!usenet
- From: erowe@mail.bayou.com (Eddie Rowe)
- Newsgroups: comp.lang.c
- Subject: Watcom String Initialization
- Date: Sat, 09 Mar 96 23:39:01 GMT
- Organization: CyberTron, Inc.
- Message-ID: <N.030996.173901.65@mail>
- NNTP-Posting-Host: p27.bayou.com
- X-Newsreader: Quarterdeck Message Center [1.0]
-
- Has anyone experienced any problems with strings initialization when using
- Watcom's compiler? I have run into incidents where LOCAL strings are not being
- initialized correctly. I can add = "" to the end of the declaration and force
- the string to be initialized, but wondered if there was something unique to
- Watcom and its handling of strings?
-
- char SomeString[20]; /*String not always initialized correctly*/
- char SomeString[20] = ""; /*String IS always initialized correctly*/
-
-
-
-
-
-
- on multiple calls to the function.
-
- I have a local character string in a function that is called multiple times
- and unless I define the string as below Watcom seems to keep the
-
-